
╔═════════╦════════════════════════════════════════════════════════════
║ GT-HELP ║ SCHEDULE.BBS - Regular tasks, and Netmail Information
╚═════════╩════════════════════════════════════════════════════════════


    You only need a SCHEDULE.BBS if you are running netmail, or have some
    other regular daily tasks which should be executed at a particular
    time.

    LINES NEEDED BY NETMAIL USERS :

   ┌────────────────────────────── ─ ─ ─
   │NET=050
   │NODE=003
   │AREA=44
   │CITY=London
   │NAME=GRAPEVINE UK, London  :  01-443 4601  (intl +44 1 443 4601).
   |

    NET and NODE node will be assigned by the netmail co-ordinator for your
    local net.

    AREA might be your country code, or other dialling prefix which your
    'local' boards show in the NODELIST but which should be stripped off
    when dialling out.

    NAME is the name of your board, and additional details you wish to
    appear on your origin line.  Best limited to 60 characters if you can.

    Note:   Two-line origins are created using a SINGLE line of typically
            140 characters.  You will need to predict where the word wrap
            occurs, taking into account that NAME= is stripped off and
            replaced by _ORIGIN:  nnn/nnn - .  Then GT will wrap it at the
            last space preceding the 80th Character.

            Do not allow your editor to word wrap a long origin line - it
            will have undesirable consequences.


    TO CONTROL USER PAGING :

    |
    │OFFICE=08:00-23:00
    |

    GT will not allow the P command outside the specified hours.


    TO CONTROL REGULAR ACTIVITIES:

    |
    │02:50-05:25 QUIT 6
    │24:02       C:\GT\MIDNIGHT
    |

    GT uses a weird '25 hour' time scale in which the times between
    midnight and 1 am are referred to as 24:xx.  For the purposes of the
    schedule.bbs file, 24:xx hours are considered to be part of the
    previous day (but do not assume this applies elswhere).

    Suffice to say that events must be in chronological order, beginning
    with the first event after 1 am and ending with the last event before
    1am the following day.  And I suggest you don't plan on having an event
    that spans 1 am.

    The TIME can either be :

        a range             as in the first example, which would cause GT
                            to execute the specified command at 2:50, or
                            whenever GT restarts between 2:50 and 5:25

        a single time       as in the second example, which would cause GT
                            to execute the command only for the duration of
                            the specified minute.
                            
    Note:   if the command takes less than the time range (or less than 
            one minute), it will be repeatedly executed until the end of 
            the period.  If this could cause a problem you should ensure 
            that the executed program runs for at least the period 
            specified - either by adding a delay or by reducing the time
            range.

    The COMMAND can either be :

        a QUIT instruction  as in the first example, which would cause GT
                            to terminate and return with the specified
                            ERRORLEVEL (6 in this case).

                            The errorlevel has to be detected by the
                            controlling batch file (eg HOST.BAT).  This
                            gives maximum DOS memory available to the
                            command, and is typically used for executing a
                            netmail batch file.  The top level batch file
                            is then responsible for restarting GT.

        a DOS command       as in the second example, which executes a
                            batch file named C:\GT\MIDNIGHT.BAT.   DOS
                            commands are executed as a shell within GT,
                            therefore MIDNIGHT.BAT automatically returns
                            control to GT when it finishes.

